Skip to content

release: PyPI distribution name → fastcrest-tether (bare 'tether' is blocked on PyPI)#222

Merged
rylinjames merged 2 commits into
mainfrom
fix/pypi-dist-name-fastcrest-tether
Jun 10, 2026
Merged

release: PyPI distribution name → fastcrest-tether (bare 'tether' is blocked on PyPI)#222
rylinjames merged 2 commits into
mainfrom
fix/pypi-dist-name-fastcrest-tether

Conversation

@rylinjames

Copy link
Copy Markdown
Collaborator

Why

pip install tether was broken site-wide because PyPI prohibits the project name tether — upload returns 400: The name 'tether' isn't allowed (reserved/blocked list, confirmed: the name 404s yet can't be registered). Published v0.12.0 as fastcrest-tether instead.

The import package (import tether) and the CLI command (tether …) are unchanged — only the pip distribution name differs. Same dist/command split reflex-vlareflex already used.

✅ Published & verified live

  • https://pypi.org/project/fastcrest-tether/0.12.0/
  • uv pip install fastcrest-tether in a clean env → tether --version prints tether 0.12.0; importlib.metadata.version('fastcrest-tether') resolves
  • twine check PASSED on both sdist + wheel; reflex compat shim still imports with its deprecation warning

Changes

  • pyproject: name = "fastcrest-tether"
  • All install specs (pip install 'tether[...]', tether @ git+…) across README, docs, install.sh, examples, launch, contrib, ci_template, ~60 Modal scripts → fastcrest-tether. CLI command strings tether … left untouched.
  • Badges + pypistats → fastcrest-tether
  • Functional metadata lookups rewired to the real dist name so they don't silently break (same bug class as fix: finish the v0.12.0 Reflex→Tether rename (repair tether-vla breakage + stale reflex text) #221): upgrade_check.distribution(), bench/eval version(), calibration _safe_pkg_version, agent/hardware._package_version (JSON key tether_version kept), comply/sbom purl+name, doctor label, telemetry User-Agent, install_digest PACKAGES.

Kept as tether

import package, CLI command + entry point, git repo + clone dir (FastCrest/tether), GHCR image, OTel service name, TETHER_* env, tether_version wire field, src/reflex shim.

🤖 Generated with Claude Code

rylinjames and others added 2 commits June 10, 2026 00:48
…ther' name is blocked on PyPI)

PyPI rejects the project name 'tether' ('isn't allowed' — reserved/blocked,
not merely taken). Published v0.12.0 as 'fastcrest-tether' instead. The import
package ('import tether') and the CLI command ('tether ...') are unchanged —
only the pip distribution name differs, the same dist/command split reflex-vla
already used.

- pyproject: name = 'fastcrest-tether'
- All 'pip install tether[...]' / 'tether @ git+...' specs across README,
  docs, install.sh, examples, launch, contrib, ci_template, and the Modal
  scripts -> 'fastcrest-tether' (CLI commands 'tether ...' left untouched)
- PyPI badges + pypistats package -> fastcrest-tether
- Functional metadata lookups rewired to the real dist name so they don't
  silently break (same bug class as #221): upgrade_check distribution(),
  bench/eval report version(), calibration _safe_pkg_version, agent/hardware
  _package_version (JSON key 'tether_version' kept), comply/sbom purl+name,
  doctor component label, telemetry User-Agent, install_digest PACKAGES

Kept as 'tether': import package, CLI command + entry point, git repo +
clone dir (FastCrest/tether), GHCR image, OTel service name, TETHER_* env,
'tether_version' wire field, src/reflex compat shim.

Published: https://pypi.org/project/fastcrest-tether/0.12.0/

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…er-*.whl

The dist-name change renamed the built wheel to fastcrest_tether-0.12.0-*.whl,
so the doctor-smoke install step's hardcoded dist/tether-*.whl glob matched
nothing ('ls: cannot access dist/tether-*.whl'). Update to the new filename.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@rylinjames rylinjames merged commit 612b487 into main Jun 10, 2026
6 checks passed
@rylinjames rylinjames deleted the fix/pypi-dist-name-fastcrest-tether branch June 10, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant